home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Mac Magazin/MacEasy 32
/
Mac Magazin and MacEasy Magazine CD - Issue 32.iso
/
Grafik & Text
/
OzTeX3.0
/
BibTeX
/
Reporting Bugs
< prev
Wrap
Text File
|
1997-02-20
|
3KB
|
84 lines
Reporting Bugs in Mac BibTeX
============================
Please send me (<mailto:darley@fas.harvard.edu>) details of:
• Machine type (PowerPC or 68k; I don't care so much which model).
• System (7/7.1/7.5/7.5.3/7.6…).
• Version of Mac BibTeX you are using (make sure it's the latest!).
• Circumstances of the bug.
Also please try repeating the bug after restarting your machine with
extensions off (hold down shift during restart). If this resolves your
problem then you have an extension conflict. You'll have to work out which
extension/control panel doesn't like BibTeX and remove it or upgrade to a
newer version.
If at all possible, please try and give me a sequence of actions which 100%
reproducibly exhibit your bug. If necessary send me .aux, .blg files etc.
There are known cosmetic bugs in which the log window is not cleared
correctly, or scrolled back to the top correctly. At least some of these
seem to be inadequacies/'features' of the Powerplant class I'm using,
which is v. annoying. I'll gradually make it work perfectly, but it's
not a high priority. So please only report peculiar bugs in that category.
thanks,
Vince.
"Not enough memory for BibTeX processing..."
============================================
This isn't a bug. BibTeX uses a lot of temporary memory to do its
processing. If it's not available, it can't run. Even if it seems there
should be enough memory available, sometimes you'll get errors. The reason
this varies is that available memory can sometimes be quite large, but
fragmented, so BibTeX can't find blocks which are big enough.
What can you do?
Use virtual memory or ram doubler, or get more memory, or quit other
applications.
What might help?
Make sure you haven't clicked the 'Big BibTeX' preferences option. It
needs even more memory at that setting.
What won't really help?
Giving BibTeX itself more memory won't help (unless you give it lots, but
then you'll have to quit other applications anyway...). It already looks
in both the system heap (temporary memory) and its own heap (the 'get info'
allocation).
Reporting Bugs when command clicking to Alpha
=============================================
If command-clicking switches you to Alpha, but what happened subsequently
seems wrong (i.e. you don't end up at the line of the error), then you
need to give me a trace of the BibTeX-Alpha interaction, as well as the
text in BibTeX's log window. Do the following:
Switch to Alpha, hit cmd-Y, hit shift-cmd-Z, select 'GURLHandler' from the
list which appears, switch back to BibTeX, repeat the problematic
cmd-click, switch to Alpha, hit cmd-Y, hit shift-cmd-D, and mail me the
trace-dump which should appear in a new window at that point. Also copy
the errant text out of BibTeX's log window, and send that to me. If no
trace-dump window appears, the problem is on the BibTeX/Appleevent end of
things, and in that case just send me the text which caused the problems.
-----------------------------
Also (for helpful souls with MacsBug):
If you are dumped into MacsBug, please grab a stack trace. You
can do this by typing:
LOG bibcrashlog
sc6
HOW
STAT
Then send me the file 'bibcrashlog' which will appear on your
desktop. Many thanks; it'll help me to track down and fix the bug.